Comparison of contrasting Prolog trace output formats

Comparison of contrasting Prolog trace output formats

This paper reports on a comparative study of three Prolog trace packages. Forty-three students of an introductory Prolog course solved five different Prolog programming problems in each of three different conditions (using isomorphic problem variants to disguise recurring tasks). Each of the three conditions provided subjects with static screen-snapshot-mockups derived from one of three differe...

Executing Trace Specifications Using Prolog

Program Trace Formats for Software Visualisation

Developers must understand a software component or piece of code before they can reuse it. Software visualisation has the potential to assist this understanding by visualising the internal structure and behaviour of components. However it is difficult to create visualisations. We create visualisations by test driving reusable components, and store the output in a formal, transportable, and filt...

Precongruence Formats for Decorated Trace Preorders

This paper explores the connection between semantic equivalences and preorders for concrete sequential processes, represented by means of labelled transition systems, and formats of transition system specifications using Plotkin’s structural approach. For several preorders in the linear time – branching time spectrum a format is given, as general as possible, such that this preorder is a precon...

Opium: An Extendable Trace Analyzer for Prolog

Traces of program executions are a helpful source of information for program debugging. They, however, give a picture of program executions at such a low level that users often have diiculties to interpret the information. Opium, our extendable trace analyzer, is connected to a \standard" Prolog tracer. Opium is programmable and extendable. It provides a trace query language and abstract views ...